Charging over an exposure function in a wireless communication network

ABSTRACT

A wireless communication network charges a user for a wireless network slice over a Network Exposure Function (NEF). A network user-plane transfers user data over the wireless network slice. In response, the network user-plane generates session data that characterizes the user data transfer over the wireless network slice. The network user-plane transfers the session data to the NEF. The NEF receives the session data and generates a service charge for the wireless network slice based on the session data. The NEF transfers the service charge for the wireless network slice and at least a portion of the session data to a distributed ledger associated with the user.

RELATED CASES

This United States patent application is a continuation of U.S. patentapplication Ser. No. 17/160,715 that was filed on Jan. 28, 2021 and isentitled “USER CHARGING OVER AN EXPOSURE FUNCTION IN A WIRELESSCOMMUNICATION NETWORK.” U.S. patent application Ser. No. 17/160,715 ishereby incorporated by reference into this United States patentapplication.

TECHNICAL BACKGROUND

Wireless communication networks provide wireless data services towireless user devices. Exemplary wireless data services includemachine-control, internet-access, media-streaming, andsocial-networking. Exemplary wireless user devices comprise phones,computers, vehicles, robots, and sensors. The wireless communicationnetworks have wireless access nodes which exchange wireless signals withthe wireless user devices over radio frequency bands. The wirelesssignals use wireless network protocols like Fifth Generation New Radio(5GNR), Long Term Evolution (LTE), Institute of Electrical andElectronic Engineers (IEEE) 802.11 (WIFI), and Low-Power Wide AreaNetwork (LP-WAN). The wireless access nodes exchange network signalingand user data with network elements that are often clustered togetherinto wireless network cores. The wireless access nodes are connected tothe wireless network cores over backhaul data links.

The wireless access nodes comprise Radio Units (RUs), Distributed Units(DUs) and Centralized Units (CUs). The RUs are mounted at elevation andhave antennas, modulators, signal processor, and the like. The RUs areconnected to the DUs which are usually nearby network computers. The DUshandle lower wireless network layers like the Physical Layer (PHY) andMedia Access Control (MAC). The DUs are connected to the CUs which arelarger computer centers that are closer to the network cores. The CUshandle higher wireless network layers like the Radio Resource Control(RRC) and Packet Data Convergence Protocol (PDCP). The CUs are coupledto network elements in the network cores. Exemplary network elementsinclude Access and Mobility Management Functions (AMFs), SessionManagement Functions (SMFs), User Plane Functions (UPFs), NetworkExposure Functions (NEFs), and Application Functions (AFs).

NEFs expose network capabilities and events to AFs. The AFs securelyinteract with user application servers to exert user control over thewireless communication network. The exposed capabilities might indicatewireless data services and their Quality-of-Service (QoS). The exposedevents might indicate service delivery and UE mobility. The userapplication servers use the AF to provision their wireless data servicesthrough the NEF. Thus, an AF may drive the NEF to provision a ProtocolData Unit (PDU) connection for a wireless user device. In some examples,the AF drives the NEF to control the entity that is charged for thewireless data service. Unfortunately, the NEF does not effectivelysupport the actual charging of the user for the wireless dataservice—the NEF only controls who gets the charge. Moreover, the NEFdoes not efficiently serve detailed session data—including servicecharges—promptly upon session delivery.

TECHNICAL OVERVIEW

A wireless communication network charges a user for a wireless networkslice over a Network Exposure Function (NEF). A network user-planetransfers user data over the wireless network slice. In response, thenetwork user-plane generates session data that characterizes the userdata transfer over the wireless network slice. The network user-planetransfers the session data to the NEF. The NEF receives the session dataand generates a service charge for the wireless network slice based onthe session data. The NEF transfers the service charge for the wirelessnetwork slice and at least a portion of the session data to adistributed ledger associated with the user.

DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a wireless communication network to charge a userover an exposure function for a wireless data service.

FIG. 2 illustrates the operation of the wireless communication networkto charge the user over the exposure function for the wireless dataservice.

FIG. 3 illustrates the operation of the wireless communication networkto charge the user over the exposure function for the wireless dataservice.

FIG. 4 illustrates a Fifth Generation (5G) communication network tocharge a user for a wireless data service over a Network ExposureFunction (NEF).

FIG. 5 illustrates a Radio Access Network (RAN) in the 5G communicationnetwork that charges the user for the wireless data service over theNEF.

FIG. 6 illustrates a 5G User Equipment (UE) in the 5G communicationnetwork that charges the user for the wireless data service over theNEF.

FIG. 7 illustrates a 5G Network Function Virtualization Infrastructure(NFVI) in the 5G communication network that charges the user for thewireless data service over the NEF.

FIG. 8 further illustrates the 5G NFVI in the 5G communication networkthat charges the user for the wireless data service over the NEF.

FIG. 9 illustrates the operation of the 5G communication network tocharge the user for the wireless data service over the NEF.

DETAILED DESCRIPTION

FIG. 1 illustrates wireless communication network 100 to charge a userfor a wireless data service over exposure function 140. Wirelesscommunication network 100 delivers a wireless data service to UE 101like internet-access, machine communications, media-conferencing, orsome other wireless network data product. Wireless communication network100 comprises wireless UE 101, Radio Access Network (RAN) 110, networkuser-plane 120, network control-plane 130, and exposure function 140.The number of UEs and RANs that are depicted on FIG. 1 has beenrestricted for clarity, and wireless communication network 100 maycomprise many more UEs and RANs.

Various examples of network operation and configuration are describedherein. In some examples, exposure function 140 exposes a servicecapability and a service charge to user data system 102. The servicecharge comprises a monetary amount or a similar value like an amount ofcredits that have a corresponding monetary amount. Exposure function 140receives a request for the service capability at the service charge fromuser data system 102, and in response, exposure function 140 maps theservice capability into network parameters and transfers the networkparameters to network control-plane 130. Network control-plane 130receives and translates the network parameters into network signaling.Network control-plane 130 transfers the network signaling to networkuser-plane 120. Network user-plane 120 exchanges user data with UE 101over RAN 110 in response to the network signaling. Network user-plane120 transfers session data that characterizes the user data transfer tonetwork control-plane 130. Network control-plane 130 transfers thesession data to exposure function 140. Exposure function 140 maps thesession data into a service delivery event that that characterizes theuser data transfer. Exposure function 140 exposes the service deliveryevent to user data system 102 to indicate the service capability and theservice charge. Advantageously, NEF 140 effectively charges user datasystem 102 for the wireless data service that was delivered to UE 101.Moreover, NEF 140 efficiently serves detailed session data to user datasystem 102 promptly upon session delivery.

In some examples, exposure function 140 receives a capability eventsubscription from user data system 102 and responsively indicates theservice capability to user data system 102. In response, exposurefunction 140 receives a request for the service capability and a servicedelivery event subscription from user data system 102. Exposure function140 maps the session data into the service delivery event in response tothe service capability request and the service delivery eventsubscription. Exposure function 140 may expose a charging capability touser data system 102 and receive a charging capability request and acharging event subscription from user data system 102. Exposure function140 maps the session data into the service delivery event that indicatesthe service charge to user data system 102 in response to the chargingcapability request and the charging event subscription. Exposurefunction 140 may expose a session detail capability to user data system102 and receive a detail capability request and a detail eventsubscription from user data system 102. Exposure function 140 maps thesession data into the service delivery event that exposes sessiondetails to user data system 102 in response to the detail capabilityrequest and the detail event subscription. Exposure function 140 mayexpose a payment capability to user data system 102 and receive paymentcapability request and a payment event subscription from user datasystem 102. Exposure function 140 receives a user paymentindication—possibly from another AF that hosts financial transactiondata. Exposure function 140 maps the session data into the servicedelivery event that indicates the user payment event to user data system102 in response to the payment capability request and the payment eventsubscription. Exposure function 140 may expose a wireless network slicecapability to user data system 102 and receive slice capability requestand a slice event subscription from user data system 102. Exposurefunction 140 maps the session data into the service delivery event thatindicates the wireless network slice in response to the slice capabilityrequest and the slice event subscription. Exposure function 140 mayexpose a wireless network policy to user data system 102 and receivepolicy capability request and a policy event subscription from user datasystem 102. Exposure function 140 maps the session data into the servicedelivery event that indicates the wireless network policy in response tothe policy capability request and the policy event subscription.

UE 101 and RAN 110 wirelessly communicate over wireless link 151 usingRadio Access Technologies (RATs) like Fifth Generation New Radio (5GNR),Long Term Evolution (LTE), Institute of Electrical and ElectronicEngineers (IEEE) 802.11 (WIFI), Low-Power Wide Area Network (LP-WAN),and/or some other wireless protocol. The RATs use electromagneticfrequencies in the low-band, mid-band, high-band, or some other portionof the electromagnetic spectrum. RAN 110 communicates with and networkuser-plane 120 and network control-plane 130 over backhaul links 152that use metallic links, glass fibers, radio channels, or some othercommunication media. Links 152-156 use IEEE 802.3 (Ethernet), TimeDivision Multiplex (TDM), Data Over Cable System Interface Specification(DOCSIS), Internet Protocol (IP), General Packet Radio Service TransferProtocol (GTP), 5GNR, LTE, WIFI, Fifth Generation Core (5GC), virtualswitching, inter-processor communication, bus interfaces, and/or someother data communication protocols.

UE 101 comprises a vehicle, sensor, robot, computer, phone, or someother data appliance with wireless communication circuitry. RAN 110 isdepicted as a tower but RAN 110 may use other mounting structures or nomounting structures at all. RAN 110 may comprise gNodeBs, eNodeBs,NB-IoT access nodes, LP-WAN base stations, wireless relays, and/or someother wireless network transceivers. UE 101 and RAN 110 compriseantennas, amplifiers, filters, modulation, and analog/digitalinterfaces. UE 101, RAN 110, user-plane 120, control-plane 130, andexposure function 140 comprise microprocessors, software, memories,transceivers, bus circuitry, and the like. The microprocessors compriseDigital Signal Processors (DSP), Central Processing Units (CPU),Graphical Processing Units (GPU), Application-Specific IntegratedCircuits (ASIC), and/or the like. The memories comprise Random AccessMemory (RAM), flash circuitry, disk drives, and/or the like. Thememories store software like operating systems, user applications, radioapplications, and network functions. The microprocessors retrieve thesoftware from the memories and execute the software to drive theoperation of wireless communication network 100 as described herein. Insome examples, user-plane 120, control-plane 130, and exposure function140 comprise Virtual Network Functions (VNFs) that are hosted by aNetwork Function Virtualization Infrastructure (NFVI).

FIG. 2 illustrates the operation of wireless communication network 100to charge the user for the wireless data service over exposure function140. The operation is exemplary and may vary in other examples. Exposurefunction 140 exposes a service capability and a service charge to userdata system 102 and receives a request for the service capability at theservice charge from user data system 102 (201). In response, exposurefunction 140 maps the service capability into network parameters andtransfers the network parameters to network control-plane 130 (202).Network control-plane 130 receives and translates the network parametersinto network signaling and transfers the network signaling to networkuser-plane 120 (203). Network user-plane 120 exchanges user data with UE101 over RAN 110 in response to the network signaling (204). Networkuser-plane 120 transfers session data that characterizes the user datatransfer to network control-plane 130 (204). Network control-plane 130transfers the session data to exposure function 140 (205). Exposurefunction 140 maps the session data into a service delivery event thatthat characterizes the user data transfer (206). Exposure function 140exposes the service delivery event to user data system 102 to indicatethe service capability the service charge (206).

FIG. 3 illustrates the operation of wireless communication network 100to charge the user for the wireless data service over exposure function140. The operation is exemplary and may vary in other examples. Exposurefunction 140 initially exposes capabilities and events to user datasystem 102 for services, charging, session detail, and payment. Exposurefunction 140 receives capability requests and event subscriptions for aservice, charging, session detail, and payment. Exposure function 140maps the requested capabilities into network parameters and transfersthe network parameters to network control-plane 130. Exposure function140 initiates the requested event reporting. Exposure function 140receives a payment indication for UE 101—possibly from an ApplicationFunction (AF) with financial transaction information. Networkcontrol-plane 130 receives the network parameters from exposure function140. Network control-plane 130 and translates the network parametersinto network signaling and exchanges network signaling with networkuser-plane 120. Network user-plane 120 exchanges network signaling anduser data with UE 101 over RAN 110. Network user-plane 120 transferssession data that characterizes the user data transfer to networkcontrol-plane 130. Network control-plane 130 transfers the session datato exposure function 140. Exposure function 140 maps the session datainto a service delivery event that that characterizes the user datatransfer based on the subscriptions. The service delivery eventindicates the service capability, service delivery, service charge,session detail, network slice, network policy, and user paymentindication. Exposure function 140 exposes the service delivery event touser data system 102 to indicate the service capability, delivery,charge, detail, slice, policy, and payment.

FIG. 4 illustrates Fifth Generation (5G) communication network 400 tocharge UE 401 for a wireless data service over Network Exposure Function(NEF) 441. 5G communication network 400 comprises an example of wirelesscommunication network 100, although network 100 may differ. 5Gcommunication network 400 comprises UE 401, Radio Access Network (RAN)410, user-plane 420, control-plane 430, NEF 441, Application Function(AF) 442, and Distributed Ledger Function (DLF) 443. RAN 110 comprisesRadio Unit (RU) 411, Distributed Unit (DU) 412, and Centralized Unit(CU) 413. User-plane 420 comprises User Plane Function (UPF) 420.Control-plane 430 comprises Access and Mobility Management Function(AMF) 431, Network Slice Selection Function (NSSF) 432, Uniform DataManagement (UDM) 433, Policy Control Function (PCF) 434, SessionManagement Function (SMF) 435, and Radio Congestion Capability Function(RCAF) 436.

External app server 402 and AF 442 communicate to securely extend AFfunctionality to external users. NEF 441 exposes capabilities to AF 442for services, charging, session detail, payment, and networkfunctionality. AF 442 transfers capability requests to NEF 441 forservices, charging, session detail, payment, and network functionality.In response to the service and charging capability requests, NEF 441exposes service capabilities and corresponding service charges to AF442. In response to the session detail capability request, NEF 441exposes available types of session detail to AF 442 like radio qualityor user mobility. In response to the payment capability request, NEF 441exposes available types of payment validation to AF 442. In response tothe network capability request, NEF 441 exposes available networkpolicies and available network slices to AF 442. NEF 441 also exposesevent subscriptions to AF 442 that are related to services, servicedelivery, session detail, charging, payment, and network functionality.NEF 441 receives capability requests and event subscriptions from AF 442for services, service delivery, session detail, charging, payment, andnetwork functionality. NEF 441 translates the requested capabilitiesinto network parameters and initiates the requested event reporting. NEF441 transfers the network parameters to NSSF 432, UDM 433, PCF 434, andSMF 435.

UE 401 wirelessly attaches to CU 413 over RU 411 and DU 412 in RAN 410.CU 413 transfer attachment signaling for UE 401 to AMF 431. AMF 431interacts with UDM 433 based on the network parameters from NEF 441 toselect wireless data services to deliver the requested servicecapabilities to UE 401. AMF 431 interacts with NSSF 432 based on thenetwork parameters from NEF 441 to select wireless network slices todeliver the selected wireless data services to UE 401. AMF 431, PCF 434,and SMF 435 interact based on the network parameters from NEF 441 toselect policies and Quality-of-Service (QoS) levels for the wirelessdata services for UE 401. SMF 435 interacts with AMF 435 based on thenetwork parameters from NEF 441 to select UPF 421—and possibly otherUPFs—to deliver the selected wireless data services to UE 401. SMF 435translates the QoS levels and other data into N4 signaling and transfersthe N4 signaling to UPF 421—and possibly other UPFs. AMF 431 translatesthe QoS and other session data into N2 signaling and transfers the N2signaling to CU 413. CU 413 signals DU 412, RU 411, and UE 401 withinstructions to deliver the wireless data services per the policies andQoS levels. AMF 431 and SMF 435 translate the policies, QoS levels, andother session data into N1 signaling and transfer the N1 signaling to UE401 over RAN 410.

UE 401 and CU 413 exchange user data over RU 411 and DU 412 to deliverthe wireless data services per the policies and QoS levels. CU 413 andUPF 421 (and possibly other UPFs) exchange the user data to deliver thewireless data services per the policies and QoS levels. UPF 421 (andpossibly other UPFs) exchange the user data with external data systemsto deliver the wireless data service per the policies and QoS levels. UE401, RU 411, DU 412, and CU 413 generate and transfer session data likeradio quality, UE mobility, data throughput, data error rate, and thelike to SMF 435 over N2/N1 signaling and AMF 431. SMF 435, AMF 431, andUPF 421 generate session data like data throughput, data amount, sessionendpoints, slice, policy, security applications, and the like. SMF 435forwards the session data to NEF 441.

NEF 441 maps the session data into service delivery events that thatcharacterize the user data transfers. The service delivery eventindicates the delivered service capabilities and delivery times. Theservice charge events indicates the cost, and the payment eventsindicate payment receipts. The slice and policy events indicate theslices and policies that were used for the wireless data services. Thesession detail event indicates metadata like radio quality, UE mobility,data throughput, error rate, data amount, session endpoints, andsecurity applications. NEF 441 exposes the service delivery events to AF442 to indicate the: requested service capabilities, service deliveries,service charges, payment indications, slices, policies, and sessiondetails like radio quality, UE mobility, wireless throughput, errorrate, data amount, data type, session endpoints, and securityapplications. AF 442 securely transfers the service delivery events toapp server 402. NEF 441 also exposes the service delivery events to DLF443.

DLF 443, ledger node 403, and other distributed ledger nodes form adistributed ledger that processes and stores the service deliveryevents. DLF 443 securely communicates with ledger node 403 and the otherdistributed ledger nodes to process the service delivery events and topropose and execute ledger transactions. DLF 443, ledger node 403, andthe other ledger nodes execute the ledger transactions and buildconsensus on the transaction results. DLF 443, ledger node 403, and theother ledger nodes each store the service delivery events and the ledgertransaction results in a blockchain format that includes a hash of theprevious block which is typically the previous service delivery event.Thus, the distributed ledger immutably stores data like the servicecapability, service delivery, service charge, payment indication, slice,policy, radio quality, UE mobility, wireless throughput, error rate,data amount, data type, session endpoints, and security applications.NEF 441 may access the distributed ledger blocks in DLF 443. App server402 may access the distributed ledger blocks in ledger node 403.

FIG. 5 illustrates Radio Access Network (RAN) 410 in the 5Gcommunication network that charges UE 401 for the wireless data serviceover NEF 441. RAN 410 comprises an example of RAN 110, although RAN 110may differ. RAN 410 comprises 5G Radio Unit (RU) 411, 5G DistributedUnit (DU) 412, and 5G Centralized Unit (CU) 413. RU 411 comprisesantennas, amplifiers, filters, modulation, analog-to-digital interfaces,DSP, memory, and transceivers (XCVRs) that are coupled over buscircuitry. DU 412 comprises memory, CPU, and transceivers that arecoupled over bus circuitry. The memory in DU 412 stores operatingsystems and 5GNR network applications like Physical Layer (PHY), MediaAccess Control (MAC), and Radio Link Control (RLC). CU 413 comprisesmemory, CPU, and transceivers that are coupled over bus circuitry. Thememory in CU 413 stores an operating system and network applicationslike Packet Data Convergence Protocol (PDCP), Service Data AdaptationProtocol (SDAP), and Radio Resource Control (RRC).

UE 401 is wirelessly coupled to the antennas in RU 411 over 5GNR links.Transceivers in RU 411 are coupled to transceivers in DU 412 overfronthaul links like enhanced Common Public Radio Interface (eCPRI).Transceivers in DU 412 are coupled to transceivers in CU 413 overmid-haul links. Transceivers in CU 413 are coupled to user-plane 420 andcontrol-plane 430 over backhaul links. The DSP in RU 411 executes anoperating system and radio applications to exchange 5GNR signals with UE401 and to exchange 5GNR data units with DU 412. The CPU in DU 412executes an operating system and PHY, MAC, and RLC to exchange 5GNR dataunits with RU 412 and to exchange 5GNR data units with CU 413. The CPUin CU 413 executes an operating system and PDCP, SDAP, and RRC toexchange 5G signaling and data with user-plane 420 and control-plane430.

On the uplink, the antennas receive wireless signals from UE 401transport uplink 5GNR signaling and data. The antennas transfercorresponding electrical signals through duplexers to the amplifiers.The amplifiers boost the received signals for filters which attenuateunwanted energy. Demodulators down-convert the amplified signals fromtheir carrier frequency. The analog/digital interfaces convert thedemodulated analog signals into digital signals for the DSP. The DSPtransfers corresponding 5GNR symbols to DU 412 over the transceivers.The PHY, MAC, and RLC in DU 412 process the uplink 5GNR symbols togenerate Service Data Units (SDUs) which are transferred to the PDCP inCU 413. In CU 413, the PDCP, SDAP, and RRC process the uplink SDUs andthe downlink 5G signaling and data to generate uplink 5G signaling anddata and downlink SDUs. The RRC exchanges N2/N1 signaling with AMF 431in control-plane 430. The SDAP exchanges N3 data with UPF 421 inuser-plane 420.

On the downlink, the PDCP in CU 413 transfers downlink SDUs to the RLCin DU 412. The RLC, MAC, and PHY process the downlink SDUs to generatedownlink 5GNR symbols. The PHY in DU 412 transfers the downlink 5GNRsymbols to the DSP in RU 411. The DSP receives downlink 5GNR symbolsfrom DU 412. The DSP processes the downlink 5GNR symbols to generatecorresponding digital signals for the analog-to-digital interfaces. Theanalog-to-digital interfaces convert the digital signals into analogsignals for modulation. Modulation up-converts the analog signals totheir carrier frequency. The amplifiers boost the modulated signals forthe filters which attenuate unwanted out-of-band energy. The filterstransfer the filtered electrical signals through duplexers to theantennas. The filtered electrical signals drive the antennas to emitcorresponding wireless signals to 5GNR UE 401 that transport thedownlink 5GNR signaling and data.

RLC functions comprise Automatic Repeat Request (ARQ), sequencenumbering and resequencing, segmentation and resegmentation. MACfunctions comprise buffer status, power control, channel quality, HybridAutomatic Repeat Request (HARQ), user identification, random access,user scheduling, and QoS. PHY functions comprise packetformation/deformation, guard-insertion/guard-deletion,parsing/de-parsing, control insertion/removal,interleaving/de-interleaving, Forward Error Correction (FEC)encoding/decoding, channel coding/decoding, channelestimation/equalization, and rate matching/de-matching,scrambling/descrambling, modulation mapping/de-mapping, layermapping/de-mapping, precoding, Resource Element (RE) mapping/de-mapping,Fast Fourier Transforms (FFTs)/Inverse FFTs (IFFTs), and DiscreteFourier Transforms (DFTs)/Inverse DFTs (IDFTs). PDCP functions includesecurity ciphering, header compression and decompression, sequencenumbering and re-sequencing, de-duplication. SDAP functions include QoSmarking and flow control. RRC functions include authentication,security, handover control, status reporting, QoS, network broadcastsand pages, and network selection.

The RRC in UE 401 attaches to the RRC in CU 413 over RU 411 and DU 412in RAN 410. The RRC in CU 413 transfers attachment signaling for UE 401to AMF 431 in control-plane 430. The RRC in CU 413 receives N2 signalingfrom AMF 431 in control-plane 430 that indicates UE session context. TheRRC in CU 413 drives DU 412 and RU 411 to deliver the wireless dataservice to UE 401 per the UE session context. The RRC in CU 413 signalsUE 401 to use the wireless data service from RU 411 per the UE context.AMF 431 and SMF 435 translate the QoS and other data into N1 signalingand transfer the N1 signaling to UE 401 over RAN 410. The SDAP in UE 401and the SDAP in CU 413 exchange user data over RU 411 and DU 412 todeliver the wireless data service per the QoS in the UE context. TheSDAP in CU 413 and UPF 421 in user-plane 420 exchange the user data todeliver the wireless data service per the QoS. UE 401, RU 411, DU 412,and CU 413 generate session data like radio quality, UE mobility, datathroughput, data error rate, and the like. The RRC in UE 401 transfersits session data to the RRC in CU 413 over RU 411 and DU 412. RU 411 andDU 412 also forward their session data to the RRC in CU 413. The RRC inCU 413 transfers the session data to SMF 435 in control-plane 430 overN2 signaling through AMF 431.

FIG. 6 illustrates 5G User Equipment (UE) 401 in 5G communicationnetwork 400 that charges UE 401 for the wireless data service over NEF441. UE 401 comprises an example of UE 101, although UE 101 may differ.UE 401 comprises 5GNR radio 601 and user circuitry 602. 5GNR radio 601comprises antennas, amplifiers, filters, modulation, analog-to-digitalinterfaces, DSP, memory, and transceivers that are coupled over buscircuitry. User circuitry 602 comprises memory, CPU, user interfaces andcomponents, and transceivers that are coupled over bus circuitry. Thememory in user circuitry 602 stores an operating system, userapplications (USER), and 5GNR network applications for PHY, MAC, RLC,PDCP, SDAP, and RRC. The antennas in 5GNR radio 601 are wirelesslycoupled to 5G RAN 510 over a carrier frequency band. A transceivers in5GNR radio 601 is coupled to a transceiver in user circuitry 602. Atransceiver in user circuitry 602 is typically coupled to userinterfaces and components like displays, controllers, and memory. TheCPU in user circuitry 602 executes the operating system, PHY, MAC, RLC,PDCP, SDAP, and RRC to exchange 5GNR signaling and data with 5G RAN 510over 5GNR radio 601.

In 5GNR radio 601, the antennas receive wireless signals from 5G RAN 410that transport downlink 5GNR signaling and data. The antennas transfercorresponding electrical signals through duplexers to the amplifiers.The amplifiers boost the received signals for filters which attenuateunwanted energy. Demodulators down-convert the amplified signals fromtheir carrier frequency. The analog/digital interfaces convert thedemodulated analog signals into digital signals for the DSPs. The DSPstransfer corresponding 5GNR symbols to user circuitry 602 over thetransceivers. In user circuitry 602, the CPU executes the networkapplications to process the 5GNR symbols and recover the downlink 5GNRsignaling and data. The 5GNR network applications receive new uplinksignaling and data from the user applications. The network applicationsprocess the uplink user signaling the downlink 5GNR signaling togenerate new downlink user signaling and new uplink 5GNR signaling. Thenetwork applications transfer the new downlink user signaling and datato the user applications. The 5GNR network applications process the newuplink 5GNR signaling and user data to generate corresponding uplink5GNR symbols that carry the uplink 5GNR signaling and data. In 5GNRradio 601, the DSPs process the uplink 5GNR symbols to generatecorresponding digital signals for the analog-to-digital interfaces. Theanalog-to-digital interfaces convert the digital uplink signals intoanalog uplink signals for modulation. Modulation up-converts the uplinkanalog signals to their carrier frequency. The amplifiers boost themodulated uplink signals for the filters which attenuate unwantedout-of-band energy. The filters transfer the filtered uplink signalsthrough duplexers to the antennas. The electrical uplink signals drivethe antennas to emit corresponding wireless 5GNR signals to 5G RAN 410that transport the uplink 5GNR signaling and data.

RRC functions comprise authentication, security, handover control,status reporting, QoS, network broadcasts and pages, and networkselection. SDAP functions comprise QoS marking and flow control. PDCPfunctions comprise security ciphering, header compression anddecompression, sequence numbering and re-sequencing, de-duplication. RLCfunctions comprise ARQ, sequence numbering and resequencing,segmentation and resegmentation. MAC functions comprise buffer status,power control, channel quality, HARQ, user identification, randomaccess, user scheduling, and QoS. PHY functions comprise packetformation/deformation, windowing/de-windowing,guard-insertion/guard-deletion, parsing/de-parsing, controlinsertion/removal, interleaving/de-interleaving, FEC encoding/decoding,channel coding/decoding, channel estimation/equalization, and ratematching/de-matching, scrambling/descrambling, modulationmapping/de-mapping, layer mapping/de-mapping, precoding, REmapping/de-mapping, FFTs/IFFTs, and DFTs/IDFTs.

FIG. 7 illustrates 5G Network Function Virtualization Infrastructure(NFVI) 700 in 5G communication network 400 that charges the UE 401 forthe wireless data service over NEF 441. NFVI 700 comprises an example ofuser-plane 120, control-plane 130, exposure function 140, althoughuser-plane 120, control-plane 130, exposure function 140 may differ.NFVI 700 comprises NFVI hardware 701, NFVI hardware drivers 702, NFVIoperating systems 703, NFVI virtual layer 704, and NFVI Virtual NetworkFunctions (VNFs) 705. NFVI hardware 701 comprises Network InterfaceCards (NICs), CPU, RAM, Flash/Disk Drives (DRIVE), and Data Switches(SW). NFVI hardware drivers 702 comprise software that is resident inthe NIC, CPU, RAM, DRIVE, and SW. NFVI operating systems 703 comprisekernels, modules, applications, containers, hypervisors, and the like.NFVI virtual layer 704 comprises vNIC, vCPU, vRAM, vDRIVE, and vSW. NFVIVNFs 705 comprise UPF 421, AMF 431, NSSF 432, UDM 433, PCF 434, SMF 435,RCAF 435, NEF 441, AF 442, and DLF 443. Other VNFs like AuthenticationServer Function (AUSF) and Network Repository Function (NRF) aretypically present but are omitted for clarity. NFVI 700 may be locatedat a single site or be distributed across multiple geographic locations.The NIC in NFVI hardware 701 are coupled to RAN 410, app server 402,ledger node 403, and other external systems. NFVI hardware 701 executesNFVI hardware drivers 702, NFVI operating systems 703, NFVI virtuallayer 704, and NFVI VNFs 705 to serve UE 401 over 5G RAN 410.

FIG. 8 further illustrates 5G NFVI 700 to charge UE 401 user for thewireless data service over NEF 441. UPF 421 performs packet routingforwarding, packet inspection. QoS handling, PDU interconnection, andmobility anchoring. AMF 431 performs N2/N1 termination, N1 ciphering &integrity protection, UE registration, SMF/PCF selection, UEconnection/mobility management, UE authentication and authorization, UEsecurity management, and tracking area updates. NSSF 432 performs slicediscovery, AMF discovery, slice authorization, and slice prioritization.User Data. Management (UDM) 433 handles UE context, UE subscriptiondata, and UE authentication keys. Policy Control Function (PCF) 434distributes UE policies to the control plane based on the requestingnetwork function. PCF 434 gives UDM 433 access to policy data. SMF 435performs session establishment/management, network address allocation,N1 termination, downlink data notification, and traffic steering androuting. RCAF 436 monitors congestion in RAN 410 and transfers RANstatus to PCF 434 and NEF 441. NEF 441 exposes network capabilities andevents to AFs, translates and abstracts data, and feeds data analytics.AF 442 securely interfaces external app server 402 to network functionslike PCF 434, NEF 441, UDM 433, and RCAF 436. DLF 443 and ledger node403 each comprise a distributed ledger node that handles ledger access,consensus, and output. DFL 443 and ledger node 403 store ledgertransactions in a blockchain format.

FIG. 9 illustrates the operation of 5G communication network 400 tocharge UE 401 for the wireless data service over NEF 441. The operationis exemplary and may vary in other examples. External app server (AS)402 and AF 442 communicate to securely extend AF functionality toexternal users. NEF 441 exposes capabilities to AF 442 for services,charging, session detail, payment, and network functionality. AF 442transfers capability requests to NEF 441 for services, charging, sessiondetail, payment, and network functionality. In response to the serviceand charging capability requests, NEF 441 exposes service capabilitiesand corresponding service charges to AF 442. In response to the sessiondetail capability request, NEF 441 exposes available types of sessiondetail to AF 442 like radio quality or user mobility. In response to thepayment capability request, NEF 441 exposes available types of paymentvalidation to AF 442. In response to the network capability request, NEF441 exposes available network policies and available network slices toAF 442. NEF 441 also exposes event subscriptions to AF 442 that arerelated to services, service delivery, session detail, charging,payment, and network functionality. NEF 441 receives capability requestsand event subscriptions from AF 442 for services, service delivery,session detail, charging, payment, and network functionality. NEF 441translates the requested capabilities into network parameters andinitiates the requested event reporting. NEF 441 transfers the networkparameters to NSSF 432, UDM 433, PCF 434, and SMF 435.

The RRC in UE 401 attaches to the RRC in CU 413. The RRC in CU 413transfers attachment signaling for UE 401 to AMF 431. AMF 431 interactswith UDM 433 based on the network parameters from NEF 441 to selectwireless data services to deliver the requested service capabilities toUE 401. AMF 431 interacts with NSSF 432 based on the network parametersfrom NEF 441 to select wireless network slices to deliver the selectedwireless data services to UE 401. AMF 431, PCF 434, and SMF 435 interactbased on the network parameters from NEF 441 to select policies andQuality-of-Service (QoS) levels for the wireless data services for UE401. SMF 435 interacts with AMF 435 based on the network parameters fromNEF 441 to select UPF 421—and possibly other UPFs—to deliver theselected wireless data services to UE 401. UE context comprises UEidentifier, addresses, QoS, network names, slices, policies, and thelike. SMF 435 transfers the UE context in N4 signaling to UPF 421—andpossibly other UPFs. AMF 431 transfers the UE context in N2 signaling tothe RRC in CU 413. The RRC in CU 413 signals DU 412, RU 411, and UE 401with instructions to deliver the wireless data services per the UEcontext. AMF 431 and SMF 435 transfer the UE context to the RRC in UE401 in N1 signaling over RAN 410. The SDAP in UE 401 and the SDAP in CU413 exchange user data deliver the wireless data services per the UEcontext. CU 413 and UPF 421 (and possibly other UPFs) exchange the userdata to deliver the wireless data service per the UE context. UPF 421exchanges the user data with external data systems to deliver thewireless data service per the UE context.

The network applications (RRC, SDAP, PDCP, RLC, MAC, PHY) in UE 401, DU412, and CU 413 generate and transfer session data (radio quality, UEmobility, data throughput, data error rate) to SMF 435 over N2/N1signaling through AMF 431. SMF 435, AMF 431, and UPF 421 generatesession data like data throughput, data amount, session endpoints,slice, policy, security applications, and the like. AMF 431 and UPF 421forward their session data to SMF 435. SMF 435 forwards all of thissession data to NEF 441.

NEF 441 maps the session data into service delivery events that thatcharacterize the user data transfers. The service delivery eventindicates the delivered service capabilities and delivery times. Theservice charge events indicates the cost, and the payment eventsindicate payment receipts. The slice and policy events indicate theslices and policies that were used for the wireless data services. Thesession detail event indicates metadata like radio quality, UE mobility,data throughput, error rate, data amount, session endpoints, andsecurity applications. NEF 441 exposes the service delivery events to AF442 to indicate the: requested service capabilities, service deliveries,service charges, payment indications, slices, policies, and sessiondetails like radio quality, UE mobility, wireless throughput, errorrate, data amount, data type, session endpoints, and securityapplications. AF 442 securely transfers the service delivery events toapp server 402. NEF 441 also exposes the service delivery events to DLF443.

DLF 443, ledger node 403, and other distributed ledger nodes form adistributed ledger that processes and stores the service deliveryevents. DLF 443 securely communicates with ledger node 403 and the otherdistributed ledger nodes to process the service delivery events and topropose and execute ledger transactions. DLF 443, ledger node 403, andthe other ledger nodes execute the ledger transactions and buildconsensus on the transaction results. DLF 443, ledger node 403, and theother ledger nodes each store the service delivery events and the ledgertransaction results in a blockchain format that includes a hash of theprevious block which is typically the previous service delivery event.Thus, the distributed ledger immutably stores data like the servicecapability, service delivery, service charge, payment indication, slice,policy, radio quality, UE mobility, wireless throughput, error rate,data amount, data type, session endpoints, and security applications.NEF 441 may access the distributed ledger blocks in DLF 443. App server402 may access the distributed ledger blocks in ledger node 403.

The wireless data network circuitry described above comprises computerhardware and software that form special-purpose network circuitry tocharge users for wireless data services over exposure functions. Thecomputer hardware comprises processing circuitry like CPUs, DSPs, GPUs,transceivers, bus circuitry, and memory. To form these computer hardwarestructures, semiconductors like silicon or germanium are positively andnegatively doped to form transistors. The doping comprises ions likeboron or phosphorus that are embedded within the semiconductor material.The transistors and other electronic structures like capacitors andresistors are arranged and metallically connected within thesemiconductor to form devices like logic circuitry and storageregisters. The logic circuitry and storage registers are arranged toform larger structures like control units, logic units, andRandom-Access Memory (RAM). In turn, the control units, logic units, andRAM are metallically connected to form CPUs, DSPs, GPUs, transceivers,bus circuitry, and memory.

In the computer hardware, the control units drive data between the RAMand the logic units, and the logic units operate on the data. Thecontrol units also drive interactions with external memory like flashdrives, disk drives, and the like. The computer hardware executesmachine-level software to control and move data by driving machine-levelinputs like voltages and currents to the control units, logic units, andRAM. The machine-level software is typically compiled from higher-levelsoftware programs. The higher-level software programs comprise operatingsystems, utilities, user applications, and the like. Both thehigher-level software programs and their compiled machine-level softwareare stored in memory and retrieved for compilation and execution. Onpower-up, the computer hardware automatically executesphysically-embedded machine-level software that drives the compilationand execution of the other computer software components which thenassert control. Due to this automated execution, the presence of thehigher-level software in memory physically changes the structure of thecomputer hardware machines into special-purpose network circuitry tocharge users for wireless data services over exposure functions.

The above description and associated figures teach the best mode of theinvention. The following claims specify the scope of the invention. Notethat some aspects of the best mode may not fall within the scope of theinvention as specified by the claims. Those skilled in the art willappreciate that the features described above can be combined in variousways to form multiple variations of the invention. Thus, the inventionis not limited to the specific embodiments described above, but only bythe following claims and their equivalents.

What is claimed is:
 1. A method of operating a wireless communicationnetwork to charge a user for a wireless network slice over a NetworkExposure Function (NEF), the method comprising: a network user-planetransferring user data over the wireless network slice, and in response,generating session data that characterizes the user data transfer overthe wireless network slice; the network user-plane transferring thesession data for delivery to the NEF; the NEF receiving the session datatransferred by the network user-plane and generating a service chargefor the wireless network slice based on the session data; and the NEFtransferring the service charge for the wireless network slice and atleast a portion of the session data for delivery to a distributed ledgerassociated with the user.
 2. The method of claim 1 further comprisingthe NEF transferring slice information that characterizes the wirelessnetwork slice for delivery to an Application Server (AS) associated withthe user.
 3. The method of claim 2 further comprising the NEF receivinga slice request for the wireless network slice transferred by the ASassociated with the user in response to the slice information.
 4. Themethod of claim 3 further comprising the NEF transferring networkparameters for delivery to a network control-plane in response toreceiving the slice request for the wireless network slice.
 5. Themethod of claim 4 further comprising: the network control-planereceiving the network parameters transferred by the NEF, generatingnetwork signaling based on the network parameters, and transferring thenetwork signaling to the network user-plane; and wherein the networkuser-plane transferring the user data over the wireless network slicecomprises transferring the user data over the wireless network slice inresponse to the network signaling.
 6. The method of claim 1 furthercomprising: the NEF transferring charging information that characterizesthe service charge for delivery to an Application Server (AS) associatedwith the user and receiving a charge request for the service chargetransferred by the AS in response to the charging information; andwherein the NEF transferring the service charge for delivery to thedistributed ledger comprises transferring the service charge fordelivery to the distributed ledger in response to receiving the chargerequest for the service charge.
 7. The method of claim 1 furthercomprising: the NEF transferring detail information that characterizessession detail for delivery to an Application Server (AS) associatedwith the user and receiving a data request for the portion of thesession data transferred by the AS in response to the detailinformation; and wherein the NEF transferring the portion of the sessiondata for delivery to the distributed ledger comprises transferring theportion of the session data for delivery to the distributed ledger inresponse to receiving the data request.
 8. The method of claim 1 furthercomprising: the NEF transferring RAN information that characterizes RANstatus for delivery to an Application Server (AS) associated with theuser and receiving a RAN request for the RAN status transferred by theAS in response to the RAN information; and wherein the NEF transferringthe portion of the session data for delivery to the distributed ledgercomprises transferring the RAN status for delivery to the distributedledger in response to receiving the RAN request.
 9. The method of claim1 further comprising: the NEF transferring policy information thatcharacterizes a network policy for delivery to an Application Server(AS) associated with the user and receiving a policy request for thenetwork policy transferred by the AS in response to the policyinformation; and wherein the NEF transferring the portion of the sessiondata for delivery to the distributed ledger comprises transferring thenetwork policy for delivery to the distributed ledger in response toreceiving the policy request.
 10. The method of claim 1 furthercomprising: the NEF receiving a payment indication that characterizes apayment of the service charge; and the NEF transferring the paymentindication for delivery to the distributed ledger.
 11. A wirelesscommunication network to charge a user for a wireless network slice overa Network Exposure Function (NEF), the wireless communication networkcomprising: a network user-plane configured to transfer user data overthe wireless network slice, and in response, generate session data thatcharacterizes the user data transfer over the wireless network slice;the network user-plane configured to transfer the session data fordelivery to the NEF; the NEF configured to receive the session datatransferred by the network user-plane and generate a service charge forthe wireless network slice based on the session data; and the NEFconfigured to transfer the service charge for the wireless network sliceand at least a portion of the session data for delivery to a distributedledger associated with the user.
 12. The wireless communication networkof claim 11 further comprising the NEF configured to transfer sliceinformation that characterizes the wireless network slice for deliveryto an Application Server (AS) associated with the user.
 13. The wirelesscommunication network of claim 12 further comprising the NEF configuredto receive a slice request for the wireless network slice transferred bythe AS in response to the slice information.
 14. The wirelesscommunication network of claim 13 further comprising the NEF configuredto transfer network parameters for delivery to a network control-planein response to receiving the slice request for the wireless networkslice.
 15. The wireless communication network of claim 14 furthercomprising: the network control-plane configured to receive the networkparameters transferred by the NEF, generate network signaling based onthe network parameters, and transfer the network signaling to thenetwork user-plane; and wherein the network user-plane is configured totransfer the user data over the wireless network slice in response tothe network signaling to transfer the user data over the wirelessnetwork slice.
 16. The wireless communication network of claim 11further comprising: the NEF configured to transfer charging informationthat characterizes the service charge for delivery to an ApplicationServer (AS) associated with the user and receive a charge request forthe service charge transferred by the AS in response to the charginginformation; and wherein the NEF is configured to transfer the servicecharge for delivery to the distributed ledger in response to receivingthe charge request to transfer the service charge for delivery to thedistributed ledger.
 17. The wireless communication network of claim 11further comprising: the NEF configured to transfer detail informationthat characterizes session detail for delivery to an Application Server(AS) associated with the user and receive a data request for the portionof the session data transferred by the AS in response to the detailinformation; and wherein the NEF is configured to transfer the portionof the session data for delivery to the distributed ledger in responseto receiving the data request to transfer the portion of the sessiondata for delivery to the distributed ledger
 18. The wirelesscommunication network of claim 11 further comprising: the NEF configuredto transfer RAN information that characterizes RAN status for deliveryto an Application Server (AS) associated with the user and receive a RANrequest for the RAN status transferred by the AS in response to the RANinformation; and wherein the NEF is configured to transfer the RANstatus for delivery to the distributed ledger in response to receivingthe RAN request to transfer the portion of the session data for deliveryto the distributed ledger.
 19. The wireless communication network ofclaim 11 further comprising: the NEF configured to transfer policyinformation that characterizes a network policy for delivery to anApplication Server (AS) associated with the user and receive a policyrequest for the network policy transferred by the AS in response to thepolicy information; and wherein the NEF is configured to transfer thenetwork policy for delivery to the distributed ledger in response toreceiving the policy request to transfer the portion of the session datafor delivery to the distributed ledger.
 20. The wireless communicationnetwork of claim 11 further comprising: the NEF configured to receive apayment indication that characterizes a payment of the service charge;and the NEF configured to transfer the payment indication for deliveryto the distributed ledger.